home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
LSD Docs
/
LSD Docs.iso
/
FILEZ
/
lsd35.dms
/
lsd35.adf
/
AmiExpress.doc.pp
/
AmiExpress.doc
Wrap
Text File
|
1990-09-13
|
102KB
|
2,422 lines
AMI-EXPRESS HOST BULLETIN BOARD SOFTWARE
----------------------------------------
Ami-Express is a host Bulletin Board software program, allowing
the transfer of data, between host and remote terminals via a
telephone link. ( Obvious to some!! ). This data can be files
uploaded or downloaded from remote (user end) from the BBS
databases. Most Bulletin boards also contain message bases where
you can read and leave electronic mail to other users. It is
possible via some BBS`s to play online games, although these are
of a simple nature, they can still be quite entertaining. For
those of you that have been a user, either host or remote, for
some time, will have noticed the major changes that Ami-Express
has undergone. With the future proposed implementations Ami-Express
will soon become comparable to other Major BBS programs found on
Amiga and PC computers.
If you own a an Illegal (Cracked copy) and you use it, then
consider buying the original. This will not only provide you with
support etc, but will encourage the further development of
Ami-Express.
-----------------------------------------------------------------------------
---------------------
Complete run-thru Doc
---------------------
This doc does a complete run thru of the bbs
and how its routines work for the August 1992
release version of AmiExpress v2.10
Special version updated by The Bird of X-TRADE
For more & Better infos Call my BBS:
Metal Decade BBS - +49-711-7775990
-----------------------------------------------------------------------------
Well, the DOCS have been needed for a long time... Well here they are.
The most difficult process in any software commericial release is the
developement of the Documentation,,, Don' get me wrong,, everyone wants
you to understand how the program works,,, It is just difficult to relate
how to do it,, so please bare with me (the author) and we may get through
this is in one piece.
AmiExpress requires 3 programs.
Program Location Description
--------- -------- -----------
Express BBS/Utils Bulletin Board System
ACP.ctrl BBS/Utils Bulletin Board controller
AE.Library LIBS/ AmiExpress Library
optional:
CONFIG BBS Configuration Program
In order to begin setting up AmiExpress, you must define how you would
like it to run. You define how you would like AmiExpress to run with the
Installation program or by modifying the ACP.Startup file. The installation
program will create the ACP.Startup file for you. It will also make a
directory called SYS:Old and store any programs it intends on overwriting.
So to begin our instructions of BBS setup I would like to explain the
ACP.Startup file.
ACP.Startup is the controller for the entire BBS, it defines who is
allowed to do what. The ACP.STARTUP needs to know the following
information:
1> The number of nodes you wish to run.
2> The way you wish the nodes to be started.
3> An instruction to load pre-made configuration files.
Here is an example of S:ACP.STARTUP:
------cut here---------------------------------------------------
NUMBER_OF_NODES 3
STARTNODE0: RUNBACK >NIL: -S50000 BBS:UTILS/EXPRESS 0
STARTNODE1: RUNBACK >NIL: -S50000 BBS:UTILS/EXPRESS 1
STARTNODE2: RUNBACK >NIL: -S50000 BBS:UTILS/EXPRESS 2
LOADCONFIG
------cut here---------------------------------------------------
NUMBER_OF_NODES x = This tells the ACP.CTRL program how many
nodes you will be running, the maximum is 9 nodes.
STARTNODEx: This tells the ACP.CTRL how to start a particular
node.. Prior users of AmiExpress probably had several script files
to start the different nodes, but now with the ACP.STARTUP
you do not need them.
LOADCONFIG: This tells the ACP.CTRL that it should load all
configuration files associated with the BBS. The configuration
files are created with a program called CONFIG. Which should be
in the BBS directory of the archive.
We highly suggest that you store AmiExpress and all associated
programs in a volume called BBS: this simplifies finding
any probs you may have. Installing AmiExpress is fairly complicated
so please be patient, even those who have run earlier version of
AmiExpress should notice a lot of setup changes, Therefore there
will not be any quick setup instructions.
CONFIG - Prior to running AmiExpress you should create a CONFIG
file for each node you are going to run, Use the program config
which is located in the BBS directory of the archive, you will
also notice in this directory that there is 3 pre-configured
CONFIG files: Config0, Config1 & Config2 we created these so you
would have an example to go by.
Here is a list of steps involved in creating a Config(x) file:
1> Copy the config program to BBS:
2> Type BBS:Config from a command line or shell.
3> Answer all of the questions to the best of your ability.
we suggest reading the complete docs to AmiExpress prior
to doing this.
a> you will need to know which node you are configuring.
4> After you have filled everything out, choose the generate
conferences option from the CONFIG menu.
5> Choose the Save File option of the CONFIG program and save
the file as BBS:ConfigX, where X indicates the node number.
Node numbers can range from 0 to 8.
In order to get everything to run, you need to add the following to your
User-StartUp file in the S: directory:
-----cut here-----------------------------------------------------
ASSIGN BBS: SYS:BBS
PATH BBS:UTILS ADD
RUNBACK >NIL: BBS:UTILS/ACP.CTRL
-----cut here-----------------------------------------------------
The above mentioned ASSIGN statement indicates that you have your
BBS installed in a directory called BBS on the system drive.
Once all of this is complete you should be able to reset your system.
NOTE: You should have a BBS:Utils directory. Use this directory to
put all amiexpress required utils, actually the only one we
have that is required in the BBS:Utils directory is the
Master Control Panel by Bryce! We are waiting an update to
MCP, the example archive shows how to set it up. Keep in mind
that BBS:Utils/MCP.script needs a S protection bit. If it does
not have one then type the following once the MCP.script is in
your BBS:Utils directory:
protect BBS:Utils/MCP.Script +s
ADVANCED FEATURES:
The ACP.CTRL program is the central hub to all bbs activity. You
may wish to customize the way it works. Here are a few additional
commands that you may put in your S:ACP.STARTUP file:
definition of NODE commands:
NODE* LEFTEDGE 0
^ ^ ^ ^
| | | ----- Specifies LEFTEDGE should = 0
| | -------------- Specifies that you wish to set the LEFTEDGE variable
| ---------------- Specifies that this command should effect all nodes
| 1> * = all nodes.
| 2> 0 = node 0 only
| 3> 1 = node 1 only etc. upto 9.
|
------------------- This is ACP.CTRL that you are executing a NODE
COMMAND.
ADVANCED COMMANDS INCLUDE: (x) & (y) indicates a value you put in.
NODE* LEFTEDGE x = This specifies the LEFTEDGE of the specified
NODE screen.
NODE* TOPEDGE x = This specifies the TOPEDGE of the specified
NODE screen.
NODE* WIDTH x = This specifies the WIDTH of the specified
NODE screen.
NODE* HEIGHT x = This specifies the HEIGHT of the specified
NODE screen.
NODE* BITPLANES x = This specifies the number of BITPLANES of the
specified node.
NODE* INTERLACE = This specifies that you wish the specified node
screen to come up in INTERLACE mode
NODE* STATBAR = This specifies that you wish each node screen
that opens to display user account information
at the top of the screen. The information includes
HANDLE,LOCATION,PASSWORD,ACCESS LEVEL, CONFERENCE
ACCESS, among other things.
NODE* LOGOFFBATCH <complete filename> = This specifies that you wish
the specified node to execute a script file every
time someone logs off.
Now open a shell and type BBS:UTILS/ACP.CTRL, You should notice a ICONIFIED
window appear on the WorkBench screen.
if ACP.CTRL did not appear on the Workbench Screen, ACP.CTRL should have
left you an error message. Please correct the error that is displayed.
Now you should click on the ZOOM gadget to the ACP.CTRL window, This will
expand the ACP window to reflect a series of buttons. To the left of the
window you should see a NODE (x) button for each NODE you want to run. You
should also notice at the upper portion of the window, 3 catagories:
'User', 'Location', 'Action', under 'Action' you should see a message
pertaining to each node saying 'Awaiting Connect'.
If you do not see the 'Awaiting Connect' message please open a shell
and type Express x (where x is the node number), this should display an
error message, most common problems is that you did not setup the
configuration file correctly, could mean that you mispelled the device
driver for the serial port, or it could be that you are missing some files.
Whatever it is, it should tell you.. Refer to later sections in this
documentation for corrective actions.
Below the node buttons you should see a series of 18 buttons. There
is 15 buttons in 3 columns on the left bottom of the window., These
buttons control AmiExpress, the way to implement one of these buttons is
to click on 1 of the 15 and then select a NODE button for action.
Now if all nodes are showing 'Awaiting Connect' do the following:
1> Press the Accounts button
2> Press the NODE 0 button
This will take you into account editing, you should see the following:
-------------------------------------
S>earch by name N>ew account editing I>nfo
Edit which account?
-------------------------------------
1> Type 1 then press <RETURN>
This will take you into account number one, which is yours.
You should see the following information:
--------------------------------------------------------------------------------
ACTIVE [1] BAUD: 14400
A> Name: User Name-------------------30 B> Location ......: Location
C> Pass ..........: Pass---8
D> Phone Number ..: 800-555-1212 (123456789)
E> Ratio .........: 0 F> Conf Access ...: X________
G> Ratio Type ....: 0 H> Sec_Level .....: 255
I> Uploads .......: 0 J> AutoReJoin ....: 1
K> Downloads .....: 0 L> Messages_Posted: 0
M> Bytes Uled ....: 1 N> New_User ......: No #Calls: 0
O> Bytes Dled ....: 0 Last Called ...: Tue May 26 22:00:17 1992
Q> Byte Limit ....: 0 Computer Type : Amiga 1000
Y> Cps Up: 0 Z> Cps DN: 0
R> Time_Limit: [9600 ] secs S> Time_Used: [0 ] secs T> UUCP: 0
X=EXIT-NOSAVE TAB=Cont ~=SAVE 1-6=Presets 9=RE-ACTIVATE DEL=DELETE
U=USER INFO
--------------------------------------------------------------------------------
2> Press the letter A, this will let you put your name on your account.
3> Press the letter B, this will let you setup a address, group name
or whatever you like.
4> Press the letter C, this will let you assign yourself a password.
5> Press the letter D, this will let you out your phone number in.
6> Now you can press a number between 1 and 6 for account defaults.
7> Make sure that your Time_Limit is not 0.
8> Press the tilde '~' to save the account,.
Here is a sample of a completed sysop account:
--------------------------------------------------------------------------------
ACTIVE [1] BAUD: 14400
A> Name: The Bird B> Location ......: Location
C> Pass ..........: Password
D> Phone Number ..: 497117775990 (123456789)
E> Ratio .........: 0 F> Conf Access ...: XXX______
G> Ratio Type ....: 0 H> Sec_Level .....: 255
I> Uploads .......: 0 J> AutoReJoin ....: 1
K> Downloads .....: 0 L> Messages_Posted: 0
M> Bytes Uled ....: 1 N> New_User ......: No #Calls: 1
O> Bytes Dled ....: 0 Last Called ...: Tue May 26 22:00:17 1992
Q> Byte Limit ....: 0 Computer Type : Amiga 1000
Y> Cps Up: 0 Z> Cps DN: 0
R> Time_Limit: [9600 ] secs S> Time_Used: [0 ] secs T> UUCP: 0
X=EXIT-NOSAVE TAB=Cont ~=SAVE 1-6=Presets 9=RE-ACTIVATE DEL=DELETE
U=USER INFO
Save
--------------------------------------------------------------------------------
9> Press the TAB key to complete the editing.
Now you should see the following:
-------------------------------------
S>earch by name N>ew account editing I>nfo
Edit which account?
-------------------------------------
10> With "I" you can get into the BBSInfo Conference witch will be describted
later..
11> Press return to exit account editing.
12> Select the close gadget to return to the WorkBench screen. This
will also of course close the BBS Window.
We will now describe the program logic of the Express so you can
learn how to operate AmiExpress to it's maximum potential.
The ACP window has 15 major buttons at the bottom of the window.
Here is a list of there names and function:
Sysop Login.........Logs you into a node as the sysop
Local Login.........Enters the initial long on phase of the Node
This will require you to specify your name
and password.
Instant Login.......This will give a carrier detect command to the
modem, this is good for re-establishing a
connection to a user after talking to them voice
on the same line.
Reserve Node........This allows you to tell the Node to only let a
certain user on the BBS. After the user has called
the node will no longer be reserved.
AEShell.............This will open a shell on the Node screen.
Accounts............This takes you into account editing on a node.
Toggle Chat ........This toggles the Node's chat request flag, if a
Nodes Chat request flag is off, then only user of
a high enough security level be able to request a
chat.
Init Modem..........This re-initializes a modem of a particular node.
Exit Node...........This will shutdown the node in question.
Node(offhook).......This will shutdown the node in question and also
make the line busy.
Node Config.........This will bring up our config program for a
particular node.
Node Chat...........This button will take you into chat mode with a
particular node.
Save Win............This button does not require a NODE(x) complement.
This simply saves the window coordinates of ACP to
a file called S:ACP.Config
Reserved............This button is reserved for future use.
^^^^^^^^^^^^^^^^^
NOTE: All of the above mentioned buttons unless said otherwise, require
you to press the Appropriate node button for them to take effect.
Once all of the NODES are started the following actions take place for
each node:
At this point the bbs will load up the computer types from a file called:
BBS:NODE(x)/COMPUTERLIST (x) indicates 1 of 9 nodes
EXAMPLE:
-----------(cut here)------------
5 <- This entry describes how many computer types follow
Amiga 500 <- 1st entry
Amiga 1000 <- 2nd entry
Amiga 2000 <- 3rd entry
Amiga 3000 <- 4th entry
Other <- 5th entry
-----------(cut here)------------
^
|
-
|
!!NOTE: The bbs and ACP require this file to exist in order to operate.!!
Now the Node will check to see if you have any logon and logoff screens.
There is an auto randomization routine for displaying screens. If you wish
to take advantage of this then you need to decide if the logon & logoff
screens are to be node specific or BBS specific, once you decide, you need
to place all Node Specific logon & logoff texts in the:
BBS:Node(x)/Screens directory.
If you wish the screens to be the same for all nodes then you them
in BBS:Screens.
NOTE that if a logon screen appears in the BBS:Node(x)/Screens directory
then the Node will use it and not bother to check if you have any in the
BBS:Screens directory.. You can say this is kind of a priority system.
If there is no logon screens in neither the BBS:Screens or
BBS:Node(x)/Screens then Express will look in the BBS:Node(x) directory.
If you plan on using the randomization screens then you will need to
put them in either the BBS:Node(x)/Screens directory or in the
BBS:Screens/ directory under the following filename syntax:
LOGON1.TXT
LOGON2.TXT
LOGON3.TXT etc...
LOGOFF1.TXT
LOGOFF2.TXT
LOGOFF3.TXT
While someone is online you have the following function keys available to
you:
F1 - Chat in/out
F2 - Increase Online time limit +10 mins
F3 - Decrease Online time limit -10 mins
F4 - Open file for capture.
F5 - Local Shell
F6 - Account Editing
F7 - Chat Flag toggle (whether you are to be paged or not)
F8 - Ser in on/off
F9 - Ser out on/off
F10 - Keyboard out on/off
F4 - Asks for a path/filename for a capture file (only on the sysops side)
or if one is already open then it closes the capture and lets you know
it did so.
SF4 - Asks for a path/filename to ASCII send a file (only on the sysops
side)
SF6 - This will let you change the Account of a User only for that call
he is online.. when he locks off the BBS will reset his Account
to the old one...
1. The bbs checks for F key input from the local keyboard.
2. Or data coming in the serial port.
3. Or data coming in the AmiExpress_Node(x) port.
4. Or data coming in from the AmiExpress window itself (Gadgets etc..)
5. Or data coming in from AmiExpress Control.(ACP)
Once a call comes in, the bbs sends an Answer string
Then awaits the response. If the resultant string is not a valid
connect string then the bbs resets the modem/screen and continues
to wait for a call
If the connect string was a valid one:
1. System checks for a file called: BBS:NODEx/NOCALLERSATb
if there is a file it displays the file then hangsup.
NOTE: x = node number, b = baudrate
2. Displays the connect string received from the modem.
3. Displays the Welcome message.
4. Check to see if you have a door called FRONTEND , if so it
executes it. see section regarding doors for more info.
Explanation:
To Install the frontend door you have to add the following
Line to the CustomCommands File:
-------Cut here----------
FRONTEND XM005DOORS:FRONT/FRONTSTATUS <<< That`s the Door !!
-------Cut here----------
5. Asks if the user wants ANSI graphics or not. If a 'Q' is
specified at the end of the line like: "YES Q" or "Y Q" etc.
Then the BBS checks if the Option Suppress_QLOGON is on or not
if the option is on the BBS will display the Logon.txt because
you want to have the users seen it .... If the Option is off and
the user answers "Y Q" or "YES Q" the BBS will not display the
logon or logoff screens....
6. Then if the sysop has specified a SYSTEM PASSWORD it
displays a file called: BBS:NODEx/PRIVATE.txt(.gr) then
asks for the SYSTEM PASSWORD. The system gives the user
three tries and if by then he hasn't gotten it the bbs
hangs up, and displays in the callerslog that someone
attempted to get the SYSTEM PASSWORD.
7. The bbs displays the file: BBS:NODEx/BBSTITLE.txt(.gr)
8. It now asks for the user to enter his FULL NAME, again wildcards
are usable and will expand and ask if correct. A user gets
five tries at his user name, then the bbs hangs up.
9. Now the BBS checks for a File called BBS:NODEx/NOTTHISNODE.TXT
and if the BBS finds such a file it will look in it and if there
is the name of the User who is online, the BBS will display
the Textfile BBS:NODEx/NOTTHISNODE.MSG and logs the user off...
10. If the bbs can't find the name supplied it will tell the user
and ask him if he would like to 'C'ontinue to join or 'R'etry
entering his name again.
User selected 'C' to continue to join as a new member.
1. If the bbs has been reserved it will notify the user that
the bbs has been reserved for a specific member and will
then hangup.
2. If the bbs hasn't been reserved then the bbs checks to see if
the user's baud rate is allowed during the time he has called.
If so, then the bbs allows the user to continue, otherwise it
displays the file: BBS:NODEx/NOTTIMEb.txt(.gr)
3. If the sysop has specified a new user password in the config
file then the bbs displays the file: BBS:NODEx/NEWUSERPW.txt(.gr)
Then it asks for the new user password and if the user gets
the password wrong it goes back and asks for his FULL NAME
again, after 5 tries the bbs hangs up.
4. The bbs now checks to see if the file: BBS:NODEx/NONEWATb
exists and if so displays that file and hangs up.
5. If the file: BBS:NODEx/NONEWUSERS exists then the bbs displays
it and then hangs up.
6. Now it enters the New Account routines.
1. Search displays BBS:NODEx/JOIN.txt(.gr)
2. Asks for full name. At this point wildcards are NOT
ALLOWED. The user only has 5 chances to enter it then
the bbs says "Too Many Errors, Goodbye!"
3. The bbs checks for use of a name that already exists.
If the name already exists it asks again.
4. The bbs checks the name given to see if not in the list
of names supplied in the file BBS:NODEx/NAMESNOTALLOWED
This is a file that contains names that the sysop does
not want to allow on the bbs. If the file does not
exists the bbs will not allow any new users to log on
util the file has been added. This is to prevent
someone getting on as ALL or EALL etc. A notice will
be placed at the end of the BBS:NODEx/CALLERSLOG file.
WARNING: You should specify in that list SYSOP, ALL, and EALL
5. Next it asks for the City, State.
6. Phone number (xxxxxxxxxxxx)
7. Password
8. Number of lines on screen (1-255)
9. Clear Screen between Messages ?
10. Display back all info and asks if it is correct if
the user needs to change something he just says no
its not correct and the process starts again at 2..
11. At this point the bbs checks to see if there is a
script questionaire to ask the user to fill out, it
checks for BBS:NODEx/SCRIPTb
NOTE: remember with the new baud rates a user could
be at 7200 9600 12000 14400 16800 so don't forget
those script files.
12. The bbs then displays the file BBS:NODEx/JOINED.txt(.gr)
10. Once the system has loaded the users account, it checks to see
if the system has been reserved, if so and the user who just logged
in is not the reserved user the bbs displays that the system has
been reserved for that specific user, and then hangs up.
11. Then the BBS will display the BBS:NODEx/LOGONx.txt(.gr) texts
12. If the bbs hasn't been reserved then the bbs checks to see if the
user's baud rate is allowed during the time he has called. If so,
then the bbs allows the user to continue, otherwise it displays
the file: BBS:NODEx/NOTTIMEb.txt(.gr)
13. If the users Security level is 0 then the bbs displays the file:
BBS:NODEx/LOCKOUT-0.txt(.gr) and then hangs up.
14. If the users Security level is 1 then the bbs displays the file:
BBS:NODEx/LOCKOUT-1.txt(.gr) and then hangs up.
13. At this point the system adds to the end of BBS:NODEx/CALLERSLOG
that a user just logged in.
14. Now the bbs asks the user for his password, every time the user
gets the password wrong the bbs adds what he tried to the end
of BBS:NODEx/CALLERSLOG
15. The user has 3 tries to enter his password if he can't the bbs
hangs up, and adds that fact to the end of BBS:NODEx/CALLERSLOG
16. The bbs checks to see if the beginning of the username starts with
"UUCP." if it does and the user has access to do UUCP, it drops
to UUCICO on the port.
17. Then the initial logon sequence takes place.
This is the initial logon sequence for a previous user:
1. The bbs checks to see if the user has any time for the day
if not it displays BBS:NODEx/LOGON24HRS.txt(.gr) file to the user
and hangs up.
2. Checks to see if there are any Node Specific Bulletins to Display to
the user.
NOTE: Routines have been added to AmiExpress to make sysop setup
a little easier and less annoying to the user. The bbs will
scan for a peticular file in this method:
Say a user with access level 30 just logged in, with ansi color...
BBS:NODEx/BULL30.txt.gr
BBS:NODEx/BULL30.txt
BBS:NODEx/BULL25.txt.gr
BBS:NODEx/BULL25.txt
BBS:NODEx/BULL20.txt.gr
BBS:NODEx/BULL20.txt
BBS:NODEx/BULL15.txt.gr
BBS:NODEx/BULL15.txt
BBS:NODEx/BULL10.txt.gr
BBS:NODEx/BULL10.txt
BBS:NODEx/BULL5.txt.gr
BBS:NODEx/BULL5.txt
BBS:NODEx/BULL.txt.gr
BBS:NODEx/BULL.txt
NOTE: because of this method of searching, all files to be
searched for must end in either 0 or 5 (as above), the
user access level will be rounded down to the nearest
multiple of 5 and the search will start there.
Thats an example of a search for a file to be displayed, once
a file is found that exists it displays ONLY that file.
This method is used on the following:
BBS:NODEx/BULL
BBS:NODEx/JOINCONF
BBS:CONF/MENU
BBS:CONF/BULL
In some cases it works a little different, in this case
the user security is not used, like:
BBS:CONF/Bulletins/BULLHELP.txt.gr
BBS:CONF/Bulletins/BULLHELP.TXT
Thats how that one works and the following are like that:
BBS:NODEx/JOINED
BBS:NODEx/LOGON24HRS
BBS:NODEx/GUESTLOGON
BBS:NODEx/LOGON
BBS:NODEx/LOGOFF
BBS:NODEx/JOIN
BBS:NODEx/NOTTIMEbaud
BBS:NODEx/PRIVATE
BBS:CONF/FILEHELP
3. Initial User specific checks are made:
A> The bbs scans thru all the conferences for mail to the user.
B> The bbs checks to see if there are any unfinished uploads.
If someone looses carrier uploading a file and calls back
he will be allowed to resume his/her upload.
4. Then the bbs rejoins the conference the user was in the last time
he called.
5. It then checks the file BBS:CONF/NDIRS to see how many, if any, directories
of files that specific conference has.
6. If the number of directories is greater than zero, the bbs looks to see
if a file exists called BBS:CONF/FREEDOWNLOADS, if so then all files in
this peticular conference are free to download.
7. Now the bbs checks for any bulletins for that conference: BBS:CONF/BULL...
NOTE: This works exactly like the BBS:NODEx/BULL files.
8. At this point the bbs has made it to the MAIN MENU PROMPT.
A> Any command entered at the MAIN MENU PROMPT will be looked up
in a BBS:CONF/Customcommands file. If the command is found as
a module name in that list then the module will be executed.
If the command cannot be found, then the command will be compared
to BBS:Commands/Customcommands and like wise be executed if found.
otherwise the command will be considered an internal command and
maybe any of the commands listed below.
NOTE: Customcommands are totally optional, If you do not have them
then don't worry.
This is a list of commands accessable from the main menu prompt:
SYSOP COMMANDS (All are access level controlled by the first
entry in AmiConfig "Account editing")
'1' - Account editing.
'2' - View Callerslog
This option will allow you to view the callerslog
file backward. That is it will display the last line
in the file first and the first line in the file last.
If you are running multinodes it will ask which node
you wish to view.
'3' - Edit file listings (w/EMACS)
This function utilizes the CLI version of EMACS to
allow you to edit the directory listings for the conference
It also checks to makesure the file exists before it
drops to the shell and loads emacs.
It is provided on the AEDISK in the UTILS directory.
NOTE: this function uses AUXx: for remote users and
CNN: for local login. Also for remote users a
watchdog utility will watch the serial port for
a loss of carrier, if the carrier is lost, within
two seconds the AMIGA will be reset.
NOTE: RemoteShell/EMACS/DOORS.
The shell call has been changed and now does not
require anything but endcli to exit the shell.
WARNING! for multinode systems, at this time the
watchdog routine will reset the AMIGA regardless
of how many nodes you are running and whether
someone is on another or not. In a later revision
a notification will go out to all other nodes and
a timeout requestor will notify you that the bbs
wants to reset the amiga, and if you are not around
the requestor will timeout and then reset, this will
be for the sysop if he is working on something and
doesn't lose his work.
WARNING! for those of you using the A2232 multi serial card
you may run into problems using the editor. We
are currently working on a fullscreen editor to
take it's place.
'4' - Edit any file on the system (w/EMACS)
Same applies to this command, it asks for a path/filename of
a file to edit.
'5' - Like Amigados LIST command.
This function does a directory of a file or a path, just like
the amigados list command. You can specify to display the
comments to the files or not.
NOTE: 5 SYS: C <-- this will do a directory of SYS:
and show comments.
'0' Remote Shell
1. If a user doesn't have access to this command it drops the
user back out to the main prompt. Also adding to the end
of BBS:NODEx/CALLERSLOG that the user failed the remote
shell password.
2. If the SYSOP specified a RemoteShell password then the
BBS asks for that password giving the user only one
chance and then put his back to the main prompt.
3. Then the bbs opens AUXx: or CNN: and starts a shell
on that device. A standard endcli will exit the shell
WARNING! for those of you who use the A2232 multi-serial
card you may run into some problems. Therefore we have
provided an Arexx Shell Interface Module. Actually we have
provided a couple of them , surely one of them will suit
your needs.
NORMAL COMMANDS (All are access level controlled by entries in the
Config or in the ACP.STARTUP)
'A' - Alter flags
This command allows you to change the flagged file list
without having to do a file listings and get a PAUSE...MORE
prompt to change the flags.
Chaining data is allowed, or the routine will prompt you.
First it will show the current list of flags.
No file flags
Filename(s) to flag: (C)lear, (Enter)=none?
At this prompt you may:
1. Enter new files to add to the flag list
2. Enter 'C' to goto the clear flag prompt
Filename(s) to Clear: (*)All, (Enter)=none?
At this prompt you may:
1. Enter filenames to remove from the flag list
wildcards are valid, however they will only
remove the first entry.
2. Using '*' will remove all enties in the list.
3. Or return to exit.
Once you've exitied the Clear prompt it will once
again show the list of flagged files and drop back
to the main menu.
'B' - Bulletins
This command allows the sysops to have bulletins for users
to read.
1. First the bbs checks to see if BBS:CONF/BULLETINS/BULLHELP.TXT
exists if not it tells the user "No bulletins are available
in this conference!"
2. The bbs then displays BBS:CONF/BULLETINS/BULLHELP.txt(.gr)
This file is a menu of the available bulletins.
3. Then the bbs asks which bulletin the user wants to view.
4. It then tries to display BBS:CONF/BULLETINS/BULLn.txt(.gr)
if it can't display it, the bbs says "Sorry there is no
bulletin #n"
'C' - Comment to SYSOP
This command is the same as entering a message, except the
message is to the SYSOP.
'D' - Download a file
1. If the number of directories in the conference is zero
then the bbs will display "No files available in this
conference." and drop the user back to the main prompt.
2. The bbs displays the File BBS:CONF/DOWNLOADMSG.txt(.gr)
3. The bbs displays the download/upload stats of the user
4. The bbs now displays the Top CPS User who has the fastest
CPS in the bbs..
5. The bbs then figures out what ratio limits the user has
left before uploading.
6. If the user had specified 'DS' and their access is 255
then they can do a SYSOP DOWNLOAD, a download of a file
from anywhere, having specified the full path/filename
7. It will then give the user a prompt to enter filenames on
8. The bbs will check to make sure the user isn't specifing
special characters like: ":/"
9. Wildcards are allowed but not without at least one normal
character EG "*" is not allowed but "a*" is allowed.
10. Now the BBS checks if there is an Comment at the File
like "RESTRICTED" or "FREE DOWNLOAD" ... if there is a
Comment like this then the BBS will display some messages
when the File has a comment like "RESTRICTED" it is not
not allowed to download this file and the bbs will write
a comment into the BBS:NODEx/CALLERSLOG that a user tried
to download this File... and with this comment you can`t
download this file with a level of 255 and sysop download
too.. so the file is 100% save for downloading... if there
is the comment "FREE DOWNLOAD" the bbs will make this file
free download and it will costs no crediz to download it...
11. As the bbs finds a file and displays the amount of time
required and how big, if the user can dl it, the bbs
automatically checks the flaglist and if there isn't already
a entry like the one just found then it adds it to the flag
list. This is so if the user wants to exit the download
routine to list a file area again, he doesn't have to type
the filenames in again. If he needs to remove one he didn't
want to download, just use 'A'lter flags command.
12. After hitting a return on a blank filespec prompt the bbs
displays the totals and checks to see if the user can download
the files within his limits.
13. Asks "(Enter) to Start, (G)oodbye after transfer, (A)bort?"
Specifing 'A'bort will exit out of the download routine.
'G'oodbye after transfer will give you 10 secs to decide
whether you really want to logoff or not.
14. At this point just as the download is about to start
if the user hasn't been added to the end of BBS:NODEx/UDLOG
then it adds him to the log.
15. If the Download finished correctly the bbs checks if the User
downloadcps was higher than the last Top Speeder User... if it
is higher the bbs will display a little text that the user is
now the fastest DownloadCps User and then write it down..
16. If the users access level is lower than 255 then his number
of downloads and bytes downloaded get updated. Look at the
ACP.STARTUP command "KEEP_UPLOAD_CREDIT" too...
17. The bbs redisplays the users stats.
'E' - Enter a message.
1. Asks for who to send it to. If a wildcard is used the search
will find the first user that fits the wildcard and will display
it and then ask if its correct, if the user says no then it
will search forward. If it doesn't find the user it will
exit back to the mainmenu prompt.
2. If the user just hits return on the TO: prompt it will send
the message to ALL.
3. A feature added in is to be able to leave a message to
"EALL" this means to EMAIL ALL people, this is only usable
by users with an access level that you specified in the
ACP.STARTUP "EALL_LEVEL". What this does is to
leave ONE message to ALL USERS , when a person calls
the system it searchs for mail in that conference to that
user it will say they have mail, from the user that left the
"EALL" message. The TO: will show the user who is receiving
the message with "(ALL)" after their name. The message can
only be deleted by the sender or a user with SYSOP access
4. Another name that is valid in the TO: prompt is SYSOP, this
will be replaced by the Name of the SYSOP, in user slot 1
5. Next prompt is the Subject of the message, if the user just
hits return it will exit out of the enter message
6. The bbs will now ask if the message is to be readable only
by the receiver of the message or it will be public.
7. Now the user has entered the message editor.
8. Tabs now work in the editor, they are indicated by a '|' in
the header.
9. Ctrl-X in the message editor will delete the current line.
10. If you hit a return on a blank line you will exit the edit
to the edit command prompt.
11. The options are:
1. A)bort - Abort entering the message
2. C)ont - Continue entering the message, this option will
print the last line with text and put the cursor
at the end of the line.
3. D)elete - Allows a user to delete a specific line.
4. E)dit - Allows the user to change text within a line.
5. F)ile - Allows a user with access 240+ to attach a file
to download to the message. This option will
ask for the filename to attach to the message
and if you wanted the file deleted with the
message as its deleted.
6. L)ist - List the message to the screen.
7. S)ave - Saves the message.
'F'ile listings
1. If the number of directories in the conference is zero
then the bbs will display "No files available in this
conference." and drop the user back to the main prompt.
2. Displays the file BBS:CONF/FILEHELP.txt(.gr) only if
all the options were not specified on the command line
3. It will then ask for the directory to list including the
'H'old directory. The hold directory can only be used
by a user with access greater than 200.
4. The specified directory will be displayed and will pause
if the NS hasn't already been specified, at the users
lines per screen point.
5. On the pause prompt, you can select 'F' for flaging files
'G'oodbye
1. First checks to see if there was a ZooMail that hasn't
been downloaded, if there was it would ask if the user
wanted to leave anyway. NOTE: ZooMail has been disabled
temporarly due to a problems with zoom being used thru
the execute command, A built in compression method is
being put together that will be FASTER and will compress
BETTER!
2. The system then checks to see if there were any partial
uploads that the user hasn't finished sending yet. If
so then it would let the user know and ask if he wanted
to leave anyway. If the user didn't want to leave, then
the bbs would ask if the user wanted to view the files.
If the user did want to view them, then the bbs would go
into the resume routine showing the user the filename
and filesize, then ask if he wanted to resume on that
peticular file. If not then the bbs would ask if the user
wanted to delete the file. If the user didn't want to
delete the file then the bbs would go to the next file
that was to be resumed.
3. If the user hadn't specified the 'Q' at the ANSI color
prompt, or the SUPPRESS_QLOGON is given the bbs would
display the file: BBS:NODEx/LOGOFF.txt(.gr)
'H'elp
1. The bbs will try to display the file BBS:BBSHELP.txt(.gr)
'I'nfo
1. With this Command the bbs displays the Top CPS Downloader
and the Top CPS Uploader...
2. Then the bbs checks if the user who locked in has a Security
Level of 255 and then it goes to the BBSInfo Conference which
will be decribed later....
'J'oin
1. The bbs will try to display BBS:NODEx/JOINCONFn.txt(.gr)
2. Ask the user for the conference number to which they want
to join. If its one they didn't have access to or the
conference didn't exist and the conference number they
entered was between 1-9 then the bbs would say:
"You do not have access to requested conference"
If the number the user entered was < 1 or > 9 then the bbs
would say "Not a valid conference number"
3. If the user had access to the conference, the bbs would
the join that conference and check for mail in that
conference.
4. The bbs would then check to see if there were any
BBS:CONF/BULLn.txt(.gr) files, if so then display the
one to the user.
'K'
This Option displays the User who is online on the other nodes
and at which baud...
'M'ode Select
This option allows the user to toggle between ANSI color and
monochrome display.
'N'ew files since.
This allows the user to list just the files that have been added
to the system since the last time they called.
1. If the number of directories in the conference is zero
then the bbs will display "No files available in this
conference." and drop the user back to the main prompt.
2. It will then ask for the date they want to list from.
The last date they were on will be the default, this is
selected by just hitting return alone. Entering the date
to list from must be done as MM-DD-YY.
3. Next the bbs asks for the directory to search thru. An 'A'
can be used to list all directories, also 'U' can be
specified for the upload directory. And H for the hold
directory. The hold directory can only be used by a user
with access greater than 200.
4. The Pause prompt works the same as described in the file
listing section.
'O'perator Page
This function is used to try to page the SYSOP to see if he's
around to chat.
1. The first time a user specifies this option his name that
is displayed in the status bar is changed to a different
color to let the sysop know that he was paged by the user
currently online.
2. If the F7 Chat toggle flag is not set to allow paging
then the bbs says:
"Sorry, The SYSOP, is not around right now
You can use 'C' to leave a comment."
3. If the chat toggle flag is set to allow paging, then the
bbs adds to BBS:NODEx/CALLERSLOG that the user paged
Then displays "Paging SYSOP (CTRL-C to Abort). ." followed
by bells and more dots.
4. If you, the SYSOP, wanted to chat with the user you would
Hit F1 to enter chat. The same F1 will exit chat when you
are finished. During chat, if ANSI mode is selected, your
text will be a different color than his.
'R'ead mail
1. First the bbs shows the read prompt
A>gain D>elete F>ile R>eply S>earch Q>uit <CR>=Next ( a+b )?
1. A>gain displays the message currently on again.
(specified by the 'a' in the above line)
2. D>elete, allows the user to delete a message only
if he left the message or the message is to him.
Also a user with access of 210+ can delete any
mail.
3. F>ile, will test if there is any Attached File to
download....
4. R>eply, allows the user to reply to a message
he just read.
5. S>earch, will display a little menu where you can
choose from :
F>rom T>o S>ubject B>ody Q>uit (b)?
1. F>rom, with this option you can search to the
whole messagebase for a Message from the User
you can insert in a prompt...
2. T>o, is the same as F>rom.. you can search the
whole messagebase for messages to the User
you can insert in a prompt
3. S>ubject, makes you able to search the whole
message base for a message with a specified
Subject....
4. B>ody, makes you able to search for a text
you can insert in a little prompt...
it will scan all messages for such a text
in it...
5. Q>uit, let you quit to the normal readmsgmenu..
6. Q>uit, exit out of the read mail routine.
7. <CR=Next>, let you continue search for new messages
8. EH - This allows the sysop to edit a messages
Header. You can change who the msg is to,
from, the subject and whether it is to be
a private message.
'S'tats for the User
This function shows the user some of his stats.
(123456789)
Conf Access: XXXXXXXXX
Caller Num.: 2049
Lst Date On: 05-14-91
Security Lv: 30
# Times On : 579
Ratio DL/UL: Disabled
# Downloads: 0
# Uploads : 0
Bytes DL'd : 0
Bytes UL'd : 1
Online Baud: 16800
Rate CPS UP: 0
Rate CPS DN: 0
Screen Clr: NO
Bytes Avail: 0
'T'ime
This function show the current time and date at the BBS
'U'pload
This function allows the user to send files to the bbs.
1. If the number of directories in the conference is zero
then the bbs will display "No files available in this
conference." and drop the user back to the main prompt.
2. If a file called BBS:CONF/UPLOADMSG.txt(.gr) exists
the bbs displays that to the user.
3. The bbs now displays the Top Upload CPS user....
4. The bbs now calculates free disk space, the first number
displayed, is the amount of free space on all the drives
listed in BBS:AMI_DRIVES
DH0:
DH1:
DH2:
DH4: <-- DH3: is not used for the bbs at all therefore
it is not in the list.
Only drives that contain download files for the bbs
should be included, this way the user knows how much
free space is left on the total system.
The second number displayed is the amount of free space
only in the BBS:CONF/UPLOAD directory. This is so the
bbs and the user know exactly how much space is available
to receive uploads until the sysop does some maintance.
Currently the bbs is content to allow uploads until the
free space in BBS:CONF/UPLOAD is less than 2000000 bytes
5. At this point the bbs calls the resume routine to check
if there are any files to resume on, this works the same
as explained under the 'G'oodbye command.
6. The bbs will then ask the user to enter the filenames of the
files he will be uploading, or he can press return alone to
have zmodem tell the bbs the names. Specifing aan 'A' will
abort out of upload altogether and drop the user back to the
main prompt.
7. If the user enters the filenames, the bbs will check to make
sure they don't already exist in the conference, if not the
bbs will ask him to enter the description for each file.
Up to 8 lines can be used to enter the description. Entering
a blank line to end the description.
8. Next the bbs will display:
(Enter) to Start, (G)oodbye after transfer, (A)bort?
this works the same as specified in the download routines.
9. At this point if the user has not been added to the end of
BBS:NODEx/UDLOG he will be.
10. If the Upload finished correctly the bbs checks if the User
uploadcps was higher than the last Top Speeder User... if it
is higher the bbs will display a little text that the user is
now the fastest UploadCps User and then write it down..
11. The bbs displays the stats from the transfer for all the
files.
12. The users time is credited for the uploads.
13. Next the bbs goes thru the files sent and checks to see if
the name is longer than 12 characters, if so the bbs asks
the user to rename the file.
14. The bbs then checks to see if the user has already given
the descriptions for the file, if so it posts it accordingly.
15. If the user has not already given the description the bbs
asks for the description for the file. Again giving 8 lines
for the description.
16. If the user gets disconnected while entering the description
the bbs will put "LOSS CARRIER" for the description.
and place the file in the BBS:CONF/LcFiles directory
along with a <username>.lc file which will contain a list
of all the files he will need to enter descriptions for
when he calls back. The Re-Enter description process is
done at log on with the PartUploads routine.
17. Once the description has been entered the bbs checks the
file extension. (a file extension is usually on 3 characters
preceeded by a '.'.)
A> Express now compares the extension if any with files
of the same extension name in the BBS:FCheck directory.
Files in the Fcheck directory specify that you are using
external file checkers. The format for each file is
as follows
----cut here----
<Checker Name>
<option> <---- if no option you must use the space.
<error text>
<error text> <---- This text should reflect what
----cut here---- the external checker will display
in the event of a bad file.
ie:
----cut here----
DMS
Test
Fatal Error
Invalid
----cut here----
^
|
------ Save this as BBS:Fcheck/DMS
If no external checker exists for the file then it
proceeds to step B.
B> if the file ends in .ARC .ZOO .LZH .WRP or .DMS and if
the sysop has that peticular testing activated, then the
bbs tests the file.
NOTE: These are the requirements for the internal testing
to work. All these programs must be in an available
path to the bbs program.
.LZH - requires LHARC version 1.31 or greater.
.ARC - requires PKAX version 1.0 or greater.
.ZOO - requires ZOO version 2.01 or greater.
.WRP and .DMS are now internal and doesn't require
anything anymore.
16. If the archive is checked and it passes the bbs puts
a 'P' between the filename and filesize in the listing.
17. If the archive is checked and if found bad then the bbs
puts a 'F' between the filename and filesize in the listing.
18. If the file is not one of the above checkable file types
then the bbs puts a 'N' between the filename and the
filesize in the listing.
19. Then the DUPE_FILECHECK option in the ACP.STARTUP comes on.
if this option is selected then prior to the file
being moved anywhere, it is bumped against a list of
filenames in either the BBS:CONF/Dir(x) or
BBS:CONF/Dir(x).Purged. If that file name is found in
the list then it will be moved to the Sysops private
hold and flagged as a 'D' duplicate file.
19. Now the bbs will post the file in a listings area. If the
user specified a '/' at the beginning of the description
for the file, or the file failed archive check, or the
user got disconnected then the bbs posts the file to the
end of BBS:CONF/HOLD/HELD If the archive passed or wasn't
checkable and the user didn't specify a '/' at the beginning
of the description then the bbs will post the file to the
end of BBS:CONF/DIRu where u is the upload directory (or
the highest directory available)
20. If when the bbs goes to move the file, like to the hold
directory and there is already a file in the hold with the
same name, the bbs will add a '_' to the end of the filename
until it can rename it to there.
21. Once all the file are exhausted the bbs checks to make sure
there aren't any free floating files in the BBS:NODEx/PLAYPEN
directory, if there are the bbs moves the files to
BBS:CONF/PARTUPLOAD as partially uploaded files from the
current user online.
'V'iew a file
This function will allow a user to view a text file, also
allow the sysop to view a file from anywhere.
1. If the number of directories in the conference is zero
then the bbs will display "No files available in this
conference." and drop the user back to the main prompt.
2. The bbs then asks the user for the filename to view.
3. If the users access is greater than 200 and he specified
'VS' instead of just 'V' then allow the filename to
include the path. The sysop view is noted at the end
of BBS:NODEx/CALLERSLOG what file was viewed.
4. The bbs then displays the file as long as the characters
in the file are < 128 in value. If a character is
greater than 127 then the bbs says "This file is not a
text file." and drops back to the main prompt.
NOTE: If a file has a comment of RESTRICTED then the user
will not be able to view the file. If an attempt was
made then the users name will be annotated in the
BBS:NODEx/CallersLog
'W'rite info
This function allows the user to change a couple of items
about himself.
1. Name : Mike Thomas
2. From : Dover, NH
3. Phone : 603-555-1212
4. Password : ??????
5. NumLines : 23
6. Computer : Amiga 2000/GVP030
7. Scrn Clr : N
'X'pert mode toggle
This function toggles whether the user is in expert mode
or novice mode. In novice mode the bbs will redisplay the
menu after every command the user issues.
'Z'ippy search
This has been updated to use a boyer-more search algorithm
which ended up increasing the zip search speed by 3 times.
It also displays the entire filelisting underwhich the
match occurred.
1. If the number of directories in the conference is zero
then the bbs will display "No files available in this
conference." and drop the user back to the main prompt.
2. Then it will ask for the string to search for, this
search is case insensitive. If the user just presses
return it will exit back to the main prompt.
3. Next it will ask for the directory to search thru, options
for this prompt are given above under 'N'ew files since.
'ZOOM' Zoo Mail
As I stated above this function has been temporarly removed
due to a problem with zoo being execute from within a program
I will be putting a compression method inside the bbs.
----------------------------------------------------------------------------
THE BBSINFO CONFERENCE
----------------------------------------------------------------------------
The BBSINFO Conference is a special conference in AmiExpress where you can
see some Datas like: Top Uploaders - Top Downloads - Userlist a.s.o.
To use this Conference you have to had a File Called BBS:BBSinfo.TXT(.gr)
this textfile can be the description for the BBSInfo Conference.... You can
get into the BBSInfo Conference in about 3 ways... the first one is you get
into account edit choose an then you can choose "I" for Info and then the bbs
displays you the BBSINFO.TXT(.gr) file and get into the BBSinfo Conference...
the second way is to press "U" when you edit a account of a user.. then the
same happens with the "I"... and the last way is to have a security level of
255 and then you can press "I" in the MainMenu an the bbs first displays you
the topCpsSpeeders then the BBSINFO.TXT(.gr) and the let you in the BBSinfo
Conference... For using this Conference it is better to turn of the Screen
Clear so that you can scroll slowly over each entry... if you don`t remove
the Screen clear it will be very hard to read the Top Uppers/downers a.s.o
But now i want to explain you the abilities of the BBSInfo Conference:
when you are in the Conference you can choose between the following options:
[1] This displays you the Top Uploaders in the BBS
[2] This displays you the Top Downloaders in the BBS
[3] This displays you the Top File Uploaders in your bbs
[4] This displays you the Top Files Downloader in your bbs
[5] This displays you all Ratios of your Users...
[6] This displays you Userlevels (High to low)
[7] This displays you the best CPS rates in Downloading
[8] This displays you the best CPS rates in Uploading
[q] this will exit the BBSInfo Conference....
With all that option you got a very good view over your bbs... So have phun
with all that options and you it very often... For better help I included
a example of the textfile in the Archive...
The Bird...
----------------------------------------------------------------------------
AREXX INTERFACE MODULE (AIM)
----------------------------------------------------------------------------
The Arexx door interface requires a file called RexxDoor, It must be in
located in your command path. This will also require an ASCII file called
CustomCommands to be either located in the conference directory or
BBS:Commands directory. The format of this file will be discussed in the
next section. RexxDoor will be launched each time an Arexx door is requested.
Note: If a CARRIER LOSS is detected or a KeyBoard timeout is detect then an
error code of 10 will be sent to the Arexx Script and RexxDoor will orderly
close any ports to the BBS and itself from the Arexx Script.
----------------------------------------------------------------------------
TRADITIONAL INTERFACE MODULE (TIM)
----------------------------------------------------------------------------
The Traditional interface provides the capability to run "DOORS" designed
for other Bulletin Board Systems. This is not to say that it will
interpret all "DOORS" but some may work. The traditional interface requires
a file called PARADOOR, which is supplied with AmiExpress and must be
located in a path that AmiExpress can find. If a CARRIER LOSS is detected
or a keyboard timeout is detected, the BBS will notify the Module, but it is
up to the Module to do an orderly halt. Most door programmers know how to
close their doors properly. AmiExpress automatically launches the PARADOOR
so please do not run it yourself.
----------------------------------------------------------------------------
AMIEXPRESS INTERFACE MODULE (XIM)
----------------------------------------------------------------------------
My interface is by far the best of all of these put together, it
allows you to do a lot of stuff. The best part about this interface is you
don't need a seperate program to access it. There will be a lot of Modules
out for this in the near future, we have several being made right now.
----------------------------------------------------------------------------
CUSTOM COMMANDS FILE FORMAT
----------------------------------------------------------------------------
Custom Commands is the key to making the new Modules work on AmiExpress
All you have to do is specify the Module name you would like users to use,
in a file called CustomCommands, this file can go in the BBS:Commands
directory or a conference directory. The BBS looks for the customcommands
in the conference the user is in prior to looking for it in BBS:Commands.
If the module is listed in the conference customcommands file then the
BBS:Commands/Customcommands file will not be considered.
The format is as follows:
__________ COMMAND TO ENTER MODULE
| _______ MODULE TYPE ( SEE BELOW FOR EXPLAINATION OF TYPES ALLOWED)
| | ________ MULTI or SINGLE NODE MODULE
| || _________ SECURITY ACCESS LEVEL
| ||| ________MODULE LOCATION AND FILENAME
| ||| |
| ||| |
v vvv v
BB XS020BBS:BulletinBoard
Bulletins XM030BBS:BulletinBoard
CoSysop XS040WORK:CoSysop/CoSysop
Test RM050bbs:rexx/test.rexx
spawn RS001pgdoors:hacker/misc/rxx.maint
hacker RM100pgdoors:hacker/hacker.strip
motel RS090pgdoors:motel/motel!
NOTE: That this is a formatted file, The module type must be in position
11 and the path and filename of the module must be in position 16.
OPTIONAL RETARD COMMANDS FORMAT
____________ TRUNCATE COMMAND COMPARISON.
| __________ COMMAND TO ENTER MODULE
| | _______ MODULE TYPE ( SEE BELOW FOR EXPLAINATION OF TYPES ALLOWED)
| | | ________ MULTI or SINGLE NODE MODULE
| | || _________ SECURITY ACCESS LEVEL
| | ||| ________MODULE LOCATION AND FILENAME
| | ||| |
| | ||| |
v v vvv v
*BB XS020BBS:BulletinBoard
*Test RM050bbs:rexx/test.rexx
MODULE TYPE - Module type may be any of the following:
X,R,P X = This means the module is an AmiExpress module.
R = This means the module is an Arexx module.
Which means RexxDoor will be called to
execute it.
P = This means the module is a Traditional module,
so the BBS will launch ParaDoor to execute this
module.
NOTE: RETARD COMMANDS- Could not think of a better name for it but the '*'
at the beginning of the module name indicates that if the first part
of the command from the menu prompt matches the module name then it
will assume you made a mistake when typing the command, Otherwise
it would not find the module name and try to execute an internal
command in the BBS.
IE: Looking above at the 'Test' Module if we did not have the '*'
then a user could accidently type 'Testit'. If this did occur
then express would not be able to locate the module named TestIt
and therefore execute the internal 'T' command which would
result in the user getting the system time instead of the test.
Using the RETARD command is a good why of overriding internal BBS
commands with commands of your own.
MCI Imbedded control sequence
Any text file may contain imbedded control sequences which will send out
variable text or cause certain things to happen.
These sequence are:
ALL COMMANDS ARE CASE SENSITIVE!!!!!!!!
MCI commands are terminated with an '|' or ' '.
MCI - Introducer
~~~~~~~~~~~~~~~~~~~~~~~~~~
~ This is the MCI introducer, this must be at the beginning of
each text file by itself inorder for Express to switch to the MCI
interpreter for displaying the text file.
MCI - User Specification -
~~~~~~~~~~~~~~~~~~~~~~~~~~
~N| User Name
~UL| User Location
~P| User Password
~#| User Phone
~TC| Total User Calls
~LC| User Last Call to the system
~M| User Message Posted
~A| User Access Level
~S| User Slot Number
~CA| User Conf. Access **** NOTE CHANGED FROM X ****
~BR| User BaudRate
~HW| User Computer Equipment
~TL| User Inital Time Limit at logon in Minutes
~TR| User Number of Mins Remaning today
~UB| User Bytes Uploaded
~DB| User Bytes Downloaded
~FU| User Files Uploaded
~FD| User Files Downloaded
~BD| User Byte Download Limit
~LG| User Logged On-Node
~Dx| Change the MCI command terminator. ie: ~D.| will change the '|' to '.'
~cx| Change foreground ansi color to anything from 0-f.
~bx| Change background ansi color to anything from 0-f.
~h| Back Space
~q| Change to default ANSI mode.
~f| Clear Screen.
~nx| Newlines where x is the number of them you would like
~~ This indicates you wish the ~ symbol to apprear, you can have as
many of them as you like after the first ~ to display them
(NOTE: no ',' on this command)
~xn| Goto X position on screen. ie: ~x10|
~yn| Goto Y position on screen. ie: ~y10|
NOTE: The above commands allow you to specify a width identifier before the
action test.. ie:
~10N| would only display the first 10 letters of the username.
MCI - System Specification -
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~SC| System Total calls
~O| Number of the other users currently Online (not implemented)
~CT| Show current Time
~DT| Show current Date
MCI - Extra Specification -
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~CR| will wait for any key to be pressed.
~CR_Prompt| will wait for and prompt the user to press any key.
ie: ~CR_PressAnyKey|
~SP| will do a standard pause, this is useful to put in between
each ~SS command.
(not implemented)~CE, Enable CTRL+C during showfile (not implemented)
(not implemented)~CD, Disable CTRL+C during showfile (not implemented)
(not implemented)~SE(x)| Turn OFF Output of screen if user has not access to conf.(x)
(not implemented)~SD(x)| Turn Output BACK on that was disabled with previous command
~SS_Name| Show <name> file. This file may also be an MCI file.
WARNING: This command could cause a serious loop problem if you
tell it to show the same file you are viewing.
WARNING: You may need to increase STACK if you nest to many of
these files.
NOTE: If this command is accessed via the message base or the
View or ViewSysop commands, then the file you are going
to view has to have a file comment of
'Allowed' or '{xxx}Allowed'
{xxx} specifies security level or above ie:
{050}Allowed, idicates that only those over or equal to
access level of 50 are allowed to view the file.
~CC_Name| Launch a door 'Name' is the door's name.
ie: ~CC_WHO| will look in conference customcommands and then
bbs:commands/customcommands
~CL| this command will display a list of conferences, commonly used
in the JoinConf.txt file
NOTE: All MCI commands have a '|' at the end except for the first initiator.
You may optionally use a ' ' instead of '|' as a terminator.
Having a line in a text file that contains:
~N|, I hope everything is going well in ~L|.
Might show:
Joseph Hodge, I hope everything is going well in Virginia.
-----------------------------------------------------------------------------
COMPLETE LIST OF NODE COMMANDS
NOTE: THIS IS A LIST OF THE COMMANDS AND DEFINITIONS
THESE COMMANDS ARE FOR THE ACP.STARTUP FILE ONLY
-----------------------------------------------------------------------------
WELCOME TO THE BRAIN OF AMIEXPRESS
---------------------------------------------------------------------
WELCOME TO THE WONDERFUL AMIEXPRESS CONFIG LANGUAGE
NOTE: The following commands are for ACP.CTRL, these
are not AmigaDos commands, so please do not try
and execute it ;)
---------------------------------------------------------------------
NOTE: All commands must begin in the 1st column of each line.
Any commands that you do not wish to implement should have
a ';' in front of it, or deleted altogether
The command NODE has the following syntax:
NODE('*'|node) - where '*' indicates all nodes and 'node'
refers to the specific node number.
ie: NODE* LEFTEDGE 0
^ ^ ^ ^
| | | ----- assign 0 to variable LEFTEDGE
| | -------- variable
| ----- All nodes
------ NODE command
---------------------------------------------------------------------
Specify task priority for acp.ctrl
ACP_PRIORITY 11
---------------------------------------------------------------------
ITop & ILeft specify the coordinates you wish to have the ACP iconfiy
window to be positioned on the WorkBench screen.
ITOP 23
ILEFT 220
---------------------------------------------------------------------
ICONIFY specifies that you wish ACP to startup in Iconify mode
ICONIFY
----------------------------------------------------------------------
NUMBER_OF_NODES, this is a must, and needs to be placed before any
NODE(x) commands, This tells ACP how many nodes your BBS has.
NUMBER_OF_NODES 3
----------------------------------------------------------------------
PUBLICSCREEN, this lets you specify a PublicScreen for ACP to run on.
If the screen cannot be found then it will default to the WorkBench
screen
;PUBLICSCREEN AEBench
----------------------------------------------------------------------
The following replacing the command line options to AmiExpress.
The only command line option that Express requires is the node number
it is going to manage.
----------------------------------------------------------------------
----------------------------------------------------------------------
LEFTEDGE..this speficies the left position of the Express window
TOPEDGE...this specifies the top position of the Express window
WIDTH.....this specifies the width of the Express window
HEIGHT....this specifies the length of the Express window
BITPLANES.this specifies the numbder of bitplanes you wish Express to
use, 0 Bitplanes will be interpreted to default to the Work
Bench screen.
NODE* LEFTEDGE 0
NODE* TOPEDGE 0
NODE* WIDTH 640
NODE* HEIGHT 200
NODE* BITPLANES 3
NODE0 BITPLANES 0
----------------------------------------------------------------------
A2232_PATCH, this command will tell express to run the A2232 Patch
routines, if you do not have a A2232 MultiSerial card, please do not
choose this option.
;NODE* A2232_PATCH
----------------------------------------------------------------------
IF LOGOFFBATCH is used, you must specify a path/filename for the
script you wish the node to execute when someone logoffs
;NODE* LOGOFFBATCH BBS:Utils/logoff.batch
----------------------------------------------------------------------
IF SHUTDOWN_BATCH is used, you must specify a path/filename for the
script you wish the node to execute when it is shutdown.
;NODE* SHUTDOWN_BATCH BBS:Utils/shutdown.batch
----------------------------------------------------------------------
STATBAR this is a ON/OFF option, if it is not specified the there
will be no account status bar for that node upon startup
;NODE* STATBAR
----------------------------------------------------------------------
EALL_LEVEL, this lets you specify the access level required to write
global provate messages. This defaults to 255 or COSYSOP LEVEL
NODE* EALL_LEVEL 220
----------------------------------------------------------------------
INTERLACE this is a ON/OFF option, if this is specified then the
node will startup in INTERLACE mode.
NODE* INTERLACE
----------------------------------------------------------------------
DUPE_FILECHECK this is a ON/OFF option, if this option is specified
then the node will check the dir(x) files and dir(x).purged files after
an upload, if the file exists in the dir(x) or dir(x).purged, the
file will be placed in the Sysops Hold directory and flagged as a
duplicate
NODE* DUPE_FILECHECK
----------------------------------------------------------------------
SUPPRESS_QLOGON this is a ON/OFF option, if this option is specified
then the node will force a user to see your logon screens.
NODE* SUPPRESS_QLOGON
----------------------------------------------------------------------
STARTNODE this command tells ACP how to start individual nodes. You
should not use the '*' in this command. Notice we do not call a script
file here, also notice that EXPRESS has the node number after it.
STARTNODE0: runback >nil: s:bbs.startup 0
STARTNODE1: runback >nil: s:bbs.startup 1
STARTNODE2: runback >nil: s:bbs.startup 2
----------------------------------------------------------------------
BUTTON - There are 15 configurable buttons on ACP, in order to config
them you need to use this command. This command is position sensitive
and must have the '|' seperator in column 24. You may configure a
NUTTON, this is a button that requires a NODE selection after it is
depressed in order to operate, a NUTTON gets the node number passed
to what ever program it is going to run
BUTTON01: AXVal |run >con:0/0/640/100//CLOSE axval <* BBS: 2 WAIT
BUTTON02: SalvUser |run >con:0/0/640/100//CLOSE salvuser <* ACP
BUTTON03: AERegCards |runback dh1:amigadex/amigadex s:AEREG.CARDS
BUTTON04: LaDraw |runback dh1:ansi/ladraw.101
-------------------------- ACCESS LEVEL CONFIG --------------------------
Access levels are very important to your BBS, Access levels range any
where from 0 to 255 with 255 being the most secure. I highly recommend
that ACCOUNT_EDITING be set at 255.
NODE* ACCOUNT_EDITING 255
----------------------------------------------------------------------
This Option lets you choose at which level the viewing of Bulletins is
allowed.
NODE* BULLETINS 10
----------------------------------------------------------------------
This Option lets you choose at which level the writing of Comments to
the SysOp is allowed.
NODE* COMMENT_TO_SYSOP 10
----------------------------------------------------------------------
This Option lets you choose at which level the User is able to
download.
NODE* DOWNLOAD 10
----------------------------------------------------------------------
This Option lets you choose at which level the User is able to upload.
NODE* UPLOAD 10
----------------------------------------------------------------------
This Option lets you choose at which level the writing of messages to
other Users is allowed.
NODE* ENTER_MESSAGE 10
----------------------------------------------------------------------
This Option lets you choose at which level the Listing of the Filelist-
ings is allowed.
NODE* FILE_LISTINGS 10
----------------------------------------------------------------------
This Option lets you choose at which level the User can join another
Conference
NODE* JOIN_CONFERENCE 10
----------------------------------------------------------------------
This Option lets you choose at which level the User can search for new
files since his last logon..
NODE* NEW_FILES_SINCE 10
----------------------------------------------------------------------
This Option lets you choose at which level the User can Page for the
Sysop...
NODE* PAGE_SYSOP 10
----------------------------------------------------------------------
This Option lets you choose at which level the User is able to read
the public messages...
NODE* READ_MSG 10
----------------------------------------------------------------------
This Option lets you choose at which level a user can use the Remote
Shell.. This is a Option which should have a 255 as the Level..
NODE* REMOTE_SHELL 255
----------------------------------------------------------------------
This Option lets you choose at which level the User is able to see his
own statistics...
NODE* DISPLAY_USER_STATS 10
----------------------------------------------------------------------
This Option lets you choose at which level the User can View a Text-
file in the bbs..
NODE* VIEW_A_FILE 10
----------------------------------------------------------------------
This Option lets you choose at which level the User can change his own
Datas into other Datas...
NODE* EDIT_USER_INFO 10
----------------------------------------------------------------------
This Option lets you choose at which level the User can change his own
handle in the bbs..
NODE* EDIT_USER_NAME 10
----------------------------------------------------------------------
This Option lets you choose at which level the User can change his own
Location where he is living..
NODE* EDIT_USER_LOCATION 10
----------------------------------------------------------------------
This Option lets you choose at which level the User can change his own
Telephonnumber he inserted before..
NODE* EDIT_PHONE_NUMBER 10
----------------------------------------------------------------------
This Option lets you choose at which level the User can change his own
and private password.
NODE* EDIT_PASSWORD 10
----------------------------------------------------------------------
This Option lets you choose at which level the User is allowed to scan
for a specified file in die Filelisting...
NODE* ZIPPY_TEXT_SEARCH 10
----------------------------------------------------------------------
This Option lets you choose at which level the User is able to page
the sysop when he is not at home..
NODE* OVERRIDE_CHAT 250
----------------------------------------------------------------------
This Options lets you choose the Colors for the SYSOP-USER chat...
The Configuration above are the best i think...
NODE* CHAT_COLOR_SYSOP 31
NODE* CHAT_COLOR_USER 32
----------------------------------------------------------------------
This Option lets you choose at which level the User can scan the
messages how goes to the Sysop...
NODE* SYSOP_READ 255
----------------------------------------------------------------------
This Option lets you choose at which level the Users Crediz will not
be updated if he is downloading something... Should be 255 !!
NODE* KEEP_UPLOAD_CREDIT 255
----------------------------------------------------------------------
This Option lets you choose at which level the User can log in every
time without looking at the START and END Times...
NODE* OVERRIDE_TIMES 255
----------------------------------------------------------------------
This Option lets you choose the TaskPriority of each Node...
NODE* TASK_PRIORITY 10
----------------------------------------------------------------------
This Options lets you choose at which time the specified User at this
baudrates can logon or not..
NODE* START_0300_TIME 0
NODE* START_1200_TIME 0
NODE* START_2400_TIME 0
NODE* START_9600_TIME 0
NODE* START_19200_TIME 0
NODE* END_0300_TIME 0
NODE* END_1200_TIME 0
NODE* END_2400_TIME 2359
NODE* END_4800_TIME 2359
NODE* END_9600_TIME 2359
NODE* END_19200_TIME 2359
----------------------------------------------------------------------
In this line you must put in your BBSName for further Operations
NODE* BBS_NAME
BYTEMASTER'S BBS
----------------------------------------------------------------------
In this line you must put in where the AmiExpress can find all his
important files.
NODE* BBS_LOCATION BBS:
----------------------------------------------------------------------
In this Line you can put in your own Handle for Paging operations a.s.o
NODE* SYSOP_NAME BYTEMASTER
-------------------------------------------------------------------------
The following commands are togglable, to turn off a feature, place a ';'
int front of the NODE command.
-------------------------------------------------------------------------
----------------------------------------------------------------------
With this Option you can turn on/off the Sent by: Comments when a User
uploaded a File..
NODE* SENTBY_FILES
----------------------------------------------------------------------
With this Option you can turn on/off the Clear Screens between a
Message..
NODE* CLEAR_SCREEN_MSG
----------------------------------------------------------------------
With this Option you can turn on/off that all the Files in a Conference
will be in Big Letters
NODE* CAPITOLS_IN_FILE
----------------------------------------------------------------------
With this Option you can turn on/off that all the User can resume a
file without your help...
NODE* ALLOW_FREE_RESUMING
----------------------------------------------------------------------
With this Option you can turn on/off the Callerslog for a specified
node in the bbs..
NODE* DO_CALLERSLOG
----------------------------------------------------------------------
With this Option you can turn on/off the UD-LOG for a specified node
NODE* DO_U/D_LOG
----------------------------------------------------------------------
With this Option you can turn on/off the registration of any shutdowning
or starting of a node which will be written down in the STARTLOG
NODE* STARTLOG
----------------------------------------------------------------------
With this Option you can turn on/off the registration of starting
any Door in Amiexpress which will be written down in the DOORLOG
NODE* DOORLOG
----------------------------------------------------------------------
With this Option you can turn on/off that when a User logged in the
AmieXpress will go automatically to the front of the screen...
NODE* SCREEN_TO_FRONT
----------------------------------------------------------------------
With that option you can turn on/off the Bulletins reading...
;NODE* ONE_TIME_BULLETINS
----------------------------------------------------------------------
With the following Options you are able to turn of the internal File
checking system for specified packed Files...
NODE* ZOO
NODE* LHARC
NODE* PKAX
NODE* WARP
NODE* ZIP
----------------------------------------------------------------------
With that option you can turn on/off that when you start a Node that
the Chatoption is on or off
;NODE* DEFAULT_CHAT_ON
----------------------------------------------------------------------
With that option you can turn on/off that the BBS lock the Baudrate to
the connection everytime a user log in..
;NODE* VARYING_LINK_RATE
-------------------------- CONFIG ACCOUNT PRESETS ------------------------
In account editing you are allowed 6 default settings per account.
PRESET_ACCESS_LVL indicates the level of access you wish to be assigned.
PRESET_RATIO_TYPE indicates the type of Ratio to be assigned. Please
refer to the documentation for ACCOUNT PRESETS
NODE* PRESET_ACCESS_LVL 01-10
NODE* PRESET_RATIO_TYPE 01-1
NODE* PRESET_RATIO 01-3
NODE* PRESET_DAILY_BYTES 01-90000
NODE* PRESET_CONF_ACCESS 01-X________
NODE* PRESET_TIME_LIMIT 01-2800
NODE* PRESET_ACCESS_LVL 02-50
NODE* PRESET_RATIO_TYPE 02-1
NODE* PRESET_RATIO 02-3
NODE* PRESET_DAILY_BYTES 02-90000
NODE* PRESET_CONF_ACCESS 02-XX_______
NODE* PRESET_TIME_LIMIT 02-3600
NODE* PRESET_ACCESS_LVL 03-100
NODE* PRESET_RATIO_TYPE 03-1
NODE* PRESET_RATIO 03-3
NODE* PRESET_DAILY_BYTES 03-90000
NODE* PRESET_CONF_ACCESS 03-XX_______
NODE* PRESET_TIME_LIMIT 03-4800
NODE* PRESET_ACCESS_LVL 04-150
NODE* PRESET_RATIO_TYPE 04-1
NODE* PRESET_RATIO 04-3
NODE* PRESET_DAILY_BYTES 04-90000
NODE* PRESET_CONF_ACCESS 04-XX_______
NODE* PRESET_TIME_LIMIT 04-9600
NODE* PRESET_ACCESS_LVL 05-200
NODE* PRESET_RATIO_TYPE 05-1
NODE* PRESET_RATIO 05-3
NODE* PRESET_DAILY_BYTES 05-90000
NODE* PRESET_CONF_ACCESS 05-XXX______
NODE* PRESET_TIME_LIMIT 05-9600
NODE* PRESET_ACCESS_LVL 06-255
NODE* PRESET_RATIO_TYPE 06-1
NODE* PRESET_RATIO 06-0
NODE* PRESET_DAILY_BYTES 06-90000
NODE* PRESET_CONF_ACCESS 06-XXX______
NODE* PRESET_TIME_LIMIT 06-9600
--------------------------- MODEM STRINGS -------------------------
;NODE* MODEM_INIT ATE0F1M0Q0V1X1S2=96S7=60S12=20B0&M4&K3&G2
NODE* MODEM_INIT ATE0F1M0Q0V1X1S0=0S2=255S7=40S12=255
NODE* MODEM_RESET ```~ATH0
NODE* MODEM_RING RING
NODE* MODEM_ANSWER ATA
NODE* CONNECT_300 CONNECT
NODE* CONNECT_1200 CONNECT 1200
NODE* CONNECT_2400 CONNECT 2400
NODE* CONNECT_4800 CONNECT 4800
NODE* CONNECT_9600 CONNECT 9600
NODE* CONNECT_19200 CONNECT 19200
----------------------------------------------------------------------
That Option makes a TRUEMODEMRESET.. that means the MODEM make a DTR
Hangup and Initalizied it again with the above Modem_INIT
;NODE* TRUE_RESET
/************************* CONFERENCE CONFIG ************************/
NODE* CONF_NAME 01-VALIDATION
NODE* CONF_LOCAL 01-BBS:VALIDATE/
NODE* CONF_NAME 02-PUBLIC DOMAIN
NODE* CONF_LOCAL 02-BBS:PD/
NODE* CONF_NAME 03-/X 2.0 SUPPORT
NODE* CONF_LOCAL 03-BBS:AE20/
NODE* CONF_NAME 04-/X 2.0 DEVELOPERS
NODE* CONF_LOCAL 04-BBS:DEVELOPE/
NODE* CONF_NAME 05-/X 2.0 BETATESTERS
NODE* CONF_LOCAL 05-BBS:BETA/
NODE* CONF_NAME 06-/X 2.0 DISTRIBUTORS
NODE* CONF_LOCAL 06-BBS:DISTRIBUTE/
NODE* CONF_NAME 07-/X 2.0 ALPHA-BETA
NODE* CONF_LOCAL 07-BBS:ALPHA/
NODE* CONF_NAME 08-/X 2.0 TOP-BRASS
NODE* CONF_LOCAL 08-BBS:BRASS/
NODE* CONF_NAME 09-RESTRICTED
NODE* CONF_LOCAL 09-BBS:RESTRICTED/
NODE* TOTAL_CONFERENCES 9
/********************** CONFERENCE CONFIG END ***********************/
NODE0 INIT_BAUD 38400
NODE2 INIT_BAUD 38400
NODE1 UNIT 2
NODE1 INIT_BAUD 19200
NODE1 DEVICE_DRIVER serial.device
NODE2 UNIT 3
NODE2 INIT_BAUD 2400
NODE2 DEVICE_DRIVER serial.device
----------------------------------------------------------------------
With the folowing options you can choose you own System - New User and
Shell Password for your BBS..
;NODE* SYSTEM PASSWORD
;NODE* NEW_USER_PASSWORD
;NODE* REMOTE_PASSWORD
/********************** BBS PROTECTION COMMANDS *********************/
----------------------------------------------------------------------
The BACKUP Option is very useful.. every time you start up your ACP.CTRL
it will make a Copy of the File you see above... it will only add a
{n} at the end of the file (where n is the number of the copy).. and if
ACP.CTRL has done 5 backups it will start again with Nr.1
BACKUP BBS:User.Data
BACKUP BBS:User.Keys
BACKUP S:ACP.STARTUP
----------------------------------------------------------------------
With this Option you can restricet some files. every time you startup
ACP.CTRL it will add the restricted Comment to file you say to it..
so you can be save that every time you start the ACP.CTRL this file can
never been downloaded..
RESTRICT BBS:COMMANDS/CUSTOMCOMMANDS
/********************** LOCATION OF IMPORTANT DATA FILES **********************/
----------------------------------------------------------------------
The following options are for placing your own user.datas.. with that
options you can rename you user.datas in another name... this is for
saving your User.Datas for a Virus or something like that...
NODE* USERDATA_LOCATION BBS:User.Data
NODE* USERKEY_LOCATION BBS:User.Keys
-----------------------------------------------------------------------------
NOTEABLE FEATURES:
1. Command history has been added in to allow up to 20 history lines
to be remembered. Once the limit of 20 has been released the
history will cycle thru. CTRL-B will reset the history pointer
to zero entries.
3. Runs only under AmigaDos 2.0. Express now supports clipping and
pasting between consoles.
4. The HELP key toggles the status bar on/off, and under AmigaDos 2.0
when you toggle the status bar on/off it auto-redisplays the text
that was in the window.
5. Locally the sysops password in the status bar is replaced with
all '?'s
6. The bbs checks to make sure the AUXx: or CNN: device can be opened
and tells the user if there is a problem.
7. A new version of Config is required to user the Baud Calling
Times.
8. Baud Calling times has been added in, kinda of a throw in and will
be changed, but for now, specify the time period a baud rate CAN
call, like to allow a baud to call all the time enter 0 for start
and 2359 for end. Start time must be a lower number than end time.
As I stated this is not perfect and will be removed from the config
and a file will contain all the times a baud can't call. It will
allow more flexiblity.
9. AREXX port 'AmiExpress_Node.x', supports the following features:
suspend - causes the bbs to close the serial port and iconify
and wait for a resume command. If someone is online
the bbs will wait util they logoff to reply to the
suspend message, and then the bbs will suspend. This
allows you to create a batch file that will automatically
suspend the bbs and load your terminal program and once
your finished with the terminal program put the bbs
back up.
resume - this command is only used while the bbs is suspended.
shutdown - this command will cause the bbs to lower the users
time online to 2 mins and tell the user that it has
received an emergency shutdown notice. Once the user
is off the bbs exits from memory.
NOTE: None of these features work without arexx.
There will be lots of AREXX commands in the future, including
node to node chatting..
10. Automatic zmodem upload, if a user starts a zmodem upload on
the main prompt the bbs will detect this and enter the zmodem
upload routines.
11. SYSOP now has the ablity to run a node in the background just
for his local use. To do this just remove the device name from
the config file and the bbs will not use the serial port. To
properly remove the serial device, click in the gadget and hit
RIGHT-AMIGA-X that will empty the gadget.
12. When the bbs asks for the number of line on the display it now
displays numbers down the side of the screen and asks the user
to enter the number he sees at the top of the screen.
13. The addition of customcommands and the Interface to program
modules has greatly added to a very flexible BBS, you could
just about run a BBS within a BBS with the power this offers
the sysop.
14. The addition of ACP has greatly enhanced AmiExpress with it's
real time monitor and ease of use.
15. CustomButtons and CustcomNuttons also enhance AmiExpress.
-----------------------------------------------------------------------------
NOTE WORTHY OF MENTION:
I would personally like to thank BullDog for letting his BBS be the
hub for this international venture. It has been tough on us both
providing the support, without BullDogs Friends BBS, AmiExpress would
not be where it is today.
I would personally like to thank Mike Thomas, who originally wrote
AmiExpress, I still do not know to this day why he choose me to carry
on with AmiExpress but I sure am appreciative, It has been a wonderful
learning experience in both the programming world and friendships.
I would personally like to thank Phil Julias for his hard work on his
original documentation for AmiExpress 1.(x) series, It has helped
considerably in the developement of the current documentation.
Enjoy the BBS, once setup will assuredly become second nature to run.
It is a fantastic program, and we all have Mike Thomas to thank for
it's creation.
AmiExpress and its source code are
copyright 1992 by Light Speed Technologies
AmiExpress is a comercial product, NOT shareware
If you used it, please buy it!
-----------------------------------
Please report any errors in this file, or any other file
in the official July 1992 AmiExpress Update to:
-----------------------------------
AmiSupport (703) 639-6114
-----------------------------------
Or Mail me:
Light Speed Technologies
P.O. Box 3016
RadFord, Virginia 24143
------------------------------------------------------------------------------
This Documentation was updated by The Bird of X-TRADE
because i don`t like the documentation of the newest Amiexpress
many options where missing...
For further information call my BBS:
__ __ __ __ __ __ __
- - /\\//\\//\\/.: X - T R A D E WORLD HEADQUARTERS :.\//\\//\\//\\/ ---
¯¯ ¯¯ ¯¯ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ¯¯ ¯¯ ¯¯
_ _ _______ _________ /~\ __
/~\ /~\ /. __ ~// __ _ ~// \ /~/
OpErAtOrS: /. \/ \// /__\//_( / / \//./\ \ /./ SySteM:
~~~~~~~~~~ // \\ // \ __/__ /.( ///__\ \//( __ ~~~~~~~
ThE BiRD \\ /\\ /\\ / \_/ \ // \ // ~ \\ \_ \_/ \ 21o MB OnLiNe
AnDy! \/ \/ \/\_____ / \\ //______ \\__/____ / 384oo bpS/OS2.0
J.J.F.! \/ \_/_~ \/ ~ \/ AMiX 2.1ø ReG
_____ _______ _______ /~\ _____ _______ BiG AMiX CoNf.!
\ ~\ /. __ ~/ /~ __ //. \ \ . ~\ /. __ ~/ ELiTE oNLY!
/. /\.\// /__\/ /. / \////\ \ // /\ \// /__\/
// / \\\ __/__// / __///__\ \// / \ \ __/__
// \__/// \_/ \\ \_/ \ ~ \\ \_ \__/ / \_/ \
\_____ /\_____ /\____ /____ \\__/___ /\_____ /
\/ \/ \/~ \/ ~ \/ \/ [SbA]
... Where the Warez come from ...
__ __ __ __ __ __ __ __ __
- - /\\//\\//\\//\\/.: [++ 49-(0)711-777-5990] :.\//\\//\\//\\//\\/ - -
¯¯ ¯¯ ¯¯ ¯¯ ¯¯ ¯¯ ¯¯ ¯¯
I hope you like this little documenatation of the newest AmiExpress...
I think i updated very much.. but still some things are missing.. so call my
bbs and we can make a better update of this Docfile...
The Bird...
------------------------------------------------------------------------------